home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
backup
/
sback1.exe
/
SBACK1.DOC
< prev
next >
Wrap
Text File
|
1993-06-08
|
21KB
|
528 lines
This README of SBACK1.ZIP is for NetWare v3.1x. The following files are
included in this revision:
WANGTEK.NLM 15681 7-18-91 3:37p
DIBIDAI.NLM 15527 7-23-92 2:14p
NOVADIBI.NLM 17119 3-31-92 12:08p
SIDR.NLM 17192 8-21-92 12:03p
TSA-310.NLM 105836 4-03-92 9:20a
TSA-311.NLM 106267 4-03-92 9:13a
TSA.NLM 27047 4-03-92 2:59p
SBACKUP.NLM 183043 3-05-92 2:00p
TAPEDAI.DSK 28838 2-08-93 5:08p
PHYSADDR.DSK 487 12-09-92 16:22p
SME-SHIM.NLM 1148 3-04-92 8:09a
SBACKUP.PCL 38199 1-15-92 11:46a(DOCUMENTATION)
SBACKUP.NFO 178176 3-12-92 3:38p(DOCUMENTATION)
SBACK1.DOC THIS FILE (Revision 1.0)
SBACKUP v3.11b Maintenance Update
These are some of SBACKUP'S fixes and enhancements.
Documentation
This update contains revised user documentation (Folioformat).To
view this documentation simply copy theSBACKUP.NFO file to the
directory where NFOLIO.EXE is located( usually SYS:PUBLIC).
Execute Nfolio.exe and select SBACKUPfrom the main menu.
3.10 NetWare support
A TSA for 3.10 NetWare is now available. Load TSA-310.NLM and
SME-SHIM.NLM on the 310 server you are backing up.
File location
The subdirectory structure under the SYS:SYSTEM directory
is not required to load NLMs. All NLMs may reside in the
SYS:SYSTEM directory*.
The directories SYS:SYSTEM\TSA (for temporary file use) and
SYS:SYSTEM\DIBI (for DIBI2$DV.DAT file) must exist.
*If the SIDR, DIBI and TSA directories are used, search paths
must be added to these directories using the SEARCH ADD
[path]command.
Restore
New restore option:
Include File Server Level - see new user document.
Bindery is NOT restored unless specifically included
using the "Include File Server Level" options.
Maintenance Improvements
» It runs faster.
» Errors no longer appear when trying to restore a directory
that does not exist.
» Corrected NameSpace data error on FTAM and NFS.
» Improved file open modes.
» Changed SMS to work on a server after the SECURE CONSOLE command.
» Corrected ABEND using SYS:\ as the working directory.
To install this new SBACKUP and supported files:
1. Flag all SBACKUP files SRW in SYS:SYSTEM.
2. Rename the SBACKUP files to *.old.
3. Copy all files to the SYS:SYSTEM directory. (In this new
version of SBACKUP, all NLMs can be loaded from the system
directory*).
*If the SIDR, DIBI and TSA directories are used, search
paths must be added to these directories using the
SEARCH ADD [path]command.
4. Flag the files back to ROS.
Explanation of TAPEDAI and DIBIDAI files:
TAPEDAI.DSK
TAPEDAI.DSK is a NetWare 386 device driver written to control
certain tape devices. It is used with DIBIDAI.NLM.
PHYSADDR.DSK is a support file for TAPEDAI.DSK and must be loaded
prior to loading TAPEDAI.DSK.
DIBIDAI.NLM presents a DIBI interface to SBACKUP.NLM, but
translates the DIBI requests into NetWare DAI calls. This
eventually results in device driver calls getting passed to
TAPEDAI.DSK through the same IO request mechanism used byNetWare
to obtain disk service.
TAPEDAI.DSK must be loaded prior to loading SBACKUP. If it is
used often, the user may want to load it from within the
STARTUP.NCF file.
In order to use TAPEDAI.DSK and DIBIDAI.NLM the DIBI2$DV.DAT
file in SYS:SYSTEM\DIBI must be edited to include DIBIDAI.NLM.
The DIBI2$DV.DAT file is a DOS text file and can be edited
using EDIT.NLM or with any DOS text editor from a workstation.
Editing the Dibi2$dv.dat file in the system\dibi subdirectory:
1. Flag the file as read/write.
2. Use a text editor to edit the file. If editing the file
using the EDIT.NLM type:
"LOAD EDIT SYS:SYSTEM\DIBI\DIBI2$DV.DAT"
at the console prompt.
3. When the file is brought up it will look like this:
"Wangtek Tape Drive." WANGTEK PORT=280 DMA=3 IRQ=5
"HP DIBI-2 Tape Driver." NOVADIBI
"DC00 DIBI-2 Tape Driver." TAPEDC00
A line like the following will need to be added:
"DibiDai Driver." DibiDai
The description on the left can be anything. The DibiDai
on the right refers to the the DibiDai.nlm that comes with
Sback.zip.
4. Exit the editor and save changes.
Dependencies:
TAPEDAI.DSK targets any ASPI compliant disk drivers. Check with
the driver manufacturer to confirm ASPI compliancy.
Consequently, the ASPI compliant disk driver must be loaded
prior to loading TAPEDAI.DSK.
Target Devices:
TAPEDAI only works with the following devices:
Manufacturer Product
ARCHIVE Python
CIPHER T826 (half inch - 2.6 Gig)
CIPHER T860 (half inch - 6 Gig)
EXABYTE EXB-8500
HP HP35450A
HP HP35470A*
HP HP35480A*
TANDBERG TDC 3800
TANDBERG TDC 4100
TANDBERG TDC 4200
WANGDAT 1300
WANGDAT 3200
WANGTEK 5525ES
WANGTEK 6130
WANGTEK WANGTEK_6130_HS
*(The HP35470A and HP35480A must be set through its dip switches
so that the SCSI Valid Bit is set upon crossing Early Warning.
If this is not done, sessions that span tapes won't be reliable.
Users should perform a test backup and restore across tapes to
confirm that the switches are set properly. The file that
actually spans tapes is the one to test.)
NOVADIBI.NLM
DIBI-2 interface driver that works with devices and drivers
that are DIBI-2 compatible. Controller driver must support
the DIBI-2 interface. Contact specific hardware vendor to
determine DIBI-2 driver compatibility.
SIDR.NLM
Storage Independent Data Requester. Controls transfer of data
between backup engine and the TSA.
TSA Files
TSA.NLM
Target Service Agent. Interface used by SIDR.NLM to
gather data from the target server.
TSA-311.NLM
Target Service Agent for 3.11 server to be backed up.
Provides link between TSA.NLM and specific 3.11 target
server.
TSA-310.NLM
Target Service Agent for 3.10 server to be backed up.
Provides link between TSA.NLM and specific 3.10 target
server. Must be used in conjunction with SME-SHIM.NLM.
SME-SHIM.NLM
Support file for TSA-310.NLM.
**********************
* A WORD OF CAUTION: *
**********************
At the present time SBackup does NO READ-AFTER-WRITE verification of the
data that is backed up. Therefore it is important that you verify your
backups manually. One way of accomplishing this is to follow example 1
in the Commonly Asked Questions section -- "How to Restore a file to a
new location." Restoring several files to a new location and doing a DOS
compare on the restored files with their originals will verify that files
are being backed up correctly and that they can be restored. It should
be kept in mind that this in no way represents a complete verification.
It is recommended that you do this with every backup set that you make
and should be made a regular step in your backup procedures.
Driver Implementation
╔═════════════════════════╤════════════════════╤════════════════════╤═════════╗
║Driver From │Driver From │Sbackup Interface │Multiple ║
║Novell │Vendor │Software │Device ║
║ │ │ │Support ║
╟─────────────────────────┼────────────────────┼────────────────────┼─────────╢
║TAPEDAI.DSK & │Any ASPI compliant │DIBIDAI.NLM (Driver │YES ║
║PHYSADDR.DSK │Disk Driver* │must be added to │ ║
║ │ │DIBI2$DV.DAT file │ ║
║ │ │-- see above │ ║
║ │ │TAPEDAI.DSK │ ║
║ │ │explanation) │ ║
╟─────────────────────────┼────────────────────┼────────────────────┼─────────╢
║B/R Driver Kit NLMs. │N/A │DC00 DIBI-2 Tape │NO ║
║(Only Adaptec.NLM │ │Driver │ ║
║Ships w/3.11 -- see │ │(TapeDC00.NLM) │ ║
║following list for other │ │ │ ║
║available drivers) │ │ │ ║
╟─────────────────────────┼────────────────────┼────────────────────┼─────────╢
║N/A │Any DIBI-2 │HP DIBI-2 Tape │YES ║
║ │Compliant Disk │Driver │ ║
║ │Driver* │(NovaDibi.NLM) │ ║
╟─────────────────────────┼────────────────────┼────────────────────┼─────────╢
║WANGTEK.NLM │N/A │Wangtek Tape Drive │N/A ║
║(Support for │ │(Wangtek.NLM) │ ║
║Wangtek's QIC-02 │ │ │ ║
║controllers) │ │ │ ║
╟─────────────────────────┼────────────────────┼────────────────────┼─────────╢
║N/A │N/A │CPQSCSIT.NLM Tape │YES ║
║ │ │driver from Compaq. │ ║
║ │ │(Must be added to │ ║
║ │ │DIBI2$DV.DAT file) │ ║
║ │ │ │ ║
║ │ │ │ ║
╟─────────────────────────┼────────────────────┼────────────────────┼─────────╢
║PS2OPT.DSK dated │N/A │DIBIDAI.NLM (Driver │YES ║
║February 4, 1993 or │ │must be added to │ ║
║later │ │DIBI2$DV.DAT file │ ║
║ │ │-- see above │ ║
║ │ │TAPEDAI.DSK │ ║
║ │ │explanation) │ ║
╚═════════════════════════╧════════════════════╧════════════════════╧═════════╝
*For verification of ASPI or DIBI-2 compliant disk drivers check with
driver vendor.
File Implementation:
Sbackup can control tape devices with the following
configurations:
1. B/R Driver Kit NLMs. Adaptec.Nlm is provided with 3.11.
The Adaptec.Nlm driver will control a single tape device
off of either an Adaptec 154x , 164x or a 174x in standard
mode.
Limitations:
» Support for only one device connected to
controller.
» Controller must be set to port address 330.
Support is also available for the following controllers with
the purchase of Novell's B/R Driver Kit (Part #153-000179-001):
THE B/R DRIVER KIT NLMs ALLOW ONLY A SINGLE DEVICE (I.E.SINGLE
TAPE DEVICE ONLY -- NO HARD DRIVES) TO BE CONNECTED TO THE
CONTROLLER.
Host Adapter Bus Interface
----------------------------------------------------------------
3COM SCSI Plus ISA SCSI
Adaptec AHA-1520 ISA SCSI
Adaptec AHA-1540 ISA SCSI
Adaptec AHA-1542 ISA SCSI
Adaptec AHA-1640 MC SCSI
Adaptec ASPI SCSI Manager SCSI
Archive VP402 ISA QIC-02
Archive VP409A MC QIC-02
BusTek BT-542B ISA SCSI
BusTek BT-642B MC SCSI
BusTek BT-742A EISA SCSI
Future Domain MCS-350 MC SCSI
Future Domain TMC-845 ISA SCSI
Future Domain TMC-850 ISA SCSI
Future Domain TMC-860 ISA SCSI
IBM SCSI Host Adapter MC SCSI
NetFRAME SCSI Adapter SCSI
Tecmar PC-02 ISA QIC-02
Tecmar PC-02 MC QIC-02
Tricord IIOP SCSI
With the B/R driver kit the NLMs can be configured for
the specific controller settings.
Implementation:
» The NLM is loaded prior to loading Sbackup.
» After loading Sbackup select the Tape DC00
driver.
NOTE: No other driver should be loaded for the
controller when using the B/R driver NLMs.
2. NovaDibi.Nlm provides tape backup support when used
in conjunction with a disk driver that is DIBI-2
compatible (to verify DIBI-2 compatibility check with
disk driver manufacturer). With the NovaDibi.nlm
driver multiple devices can be connected to the
controller.
Implementation:
» Load DIBI-2 compliant disk driver before
loading Sbackup.
» Load TSA.
» Select the HP-Dibi2 Tape Driver option in
Sbackup.
This driver was developed initially for the HP DAT
drives. Caution should be used when using a
"Non-DAT" drive. Errors could occur when multiple
sessions are backed up to a single tape.
3. TapeDai.DSK and PhysAddr.Nlm provide tape backup
support when used in conjunction with an ASPI
compliant disk driver (to verify disk driver's ASPI
compliancy contact driver manufacturer).
Implementation:
» Load ASPI compliant disk driver.
» Load PHYSADDR.DSK
» Load TapeDai.Dsk.
» Select DibiDai.Nlm option that was
added to DIBI2$DV.DAT file (for
instructions on how to edit file
see note about DibiDai.Nlm file
above).
NOTE: If the tape drive being used is not in the
list of tape drives supported by TapeDai.Dsk
this configuration will NOT work.
4. Wangtek.Nlm. Provides tape backup support for Wangtek's
QIC-02 tape devices. The default setting for the driver
is Port=280, DMA=3, IRQ=5. If the QIC-02 adapter is
set to anything other than these settings the
DIBI2$DV.DAT file will need to be edited (see
instructions above for editing the DIBI2$DV.DAT file).
5. PS2Opt.Dsk dated February 4, 1993 and DIBIDAI.NLM.
This driver is included in documentation due to its
unique implementation.
» Load PS2Opt.Dsk.
» Load TSA
» Load Sbackup
» Select DibiDai.Nlm option that was
added to DIBI2$DV.DAT file (for
instructions on how to edit file see
note about DibiDai.Nlm file above).
Requirements:
» PS2OPT.DSK dated 02-04-93 or later.
» PS2OPT.DSK has only been tested with the
following devices:
1. Exabyte 8200, 8mm
2. Exabyte 8500, 8mm
3. HP 35470, 4mm DAT
4. HP 35480A, 4mm DAT
5. HP 35450A, 4mm DAT
6. WangDat 3200, 4mm DAT
7. WangDat 1300, 4mm DAT
8. Archive Python, 4mm DAT
9. Cipher T860s, 1/2 inch tape
6. CPQSCSIT.NLM. Driver can be found on Compaq's Netware
Programs diskette or the latest driver can be obtained
from Netwire -- CPQTAP.ZIP in library 13. This driver
allows Sbackup to function with the following Compaq
tape drives:
Drive Name Part Number
320-/525-MG Tape Drive 116573-001
1.3-/2.0-GB DAT Drive 131162-001
In order to use this driver the DIBI2$DV.DAT file in the
SYS:SYSTEM\DIBI subdirectory must be editted (see note
for editting the DIBI2$DV.DAT file above).
If server is EISA based the following line will need to
be added:
"Compaq SCSI Tape Driver." CPQSCSIT
If server is ISA base the following line will need to be
added:
"Compaq SCSI Tape Driver." CPQSCSIT PORT=xxx DMA=x IRQ=x
The x's after PORT, DMA and IRQ should be replaced with
the actual setting of the SCSI tape adapter. CPQSCSIT
should also be lined up with the other driver names in
the DIBI2$DV.DAT file.
Implementation:
» Load TSA
» Load Sbackup
» Select Compaq Option that was added to the
DIBI2$DV.DAT file.
Commonly Asked Questions:
1. How to restore a file to a new location.
From the Sbackup Restore Options Menu select "Selection List
Options."
With the "Include Directories" Option insert the name
of the subdirectory that files are to be redirected TO
(i.e. the destination subdirectory).
With the "Include and Exclude File" Options select
specific files to be redirected.
With the "Destination Paths" Option insert the"Source"
and "Destination" paths.
Start the Restore.
EXAMPLE:
Files that were backed up in the SYS:FIRST subdirectory
with the file specification of *.DATneed to be restored
to the VOL1:SECOND subdirectory.On the Sbackup Restore
Options Menu select"Selection List Options."
Set the "Include Directories" Option to VOL1:SECOND --
the name of the destination subdirectory.
Set the "Include Files" Option to *.DAT -- the file
specification to be restored.
Escape back to the Restore Options Menu and select
"Destination Paths."
Press Insert and enter the "Path Source" as SYS:FIRST.
Enter the "Path Destination " as VOL1:SECOND.
Start the Restore.
2. How to Restore specific files.
From the Sbackup Restore Options Menu select "Selection
List Options."
With the "Include Directories" Option insert the
directory in which the file to be restored resided when
it was backed up. If you don't know leave this option
blank -- all directories will be searched for the include
files specified.
With the "Include Files" Option insert the filenames to be
restored. Wild cards (* and ?) can be used.
Start the Restore.
EXAMPLE:
The entire SYS:TEMP subdirectory was deleted and purged.
The entire subdirectory does not need to be restored only
spreadsheet files need to be restored.
On the Sbackup Restore Options Menu select "Selection
List Options."
The "Include Directories" option would be set to SYS:TEMP.
This will prevent Sbackup from restoring all instances of
the spreadsheet files.
The "Include Files" option would be set to *.WKS, the
extension of the spreadsheet files.
Start the Restore.
3. In the "Selection List Options" which takes precedence over
the other "Include" or "Exclude"?
The "Exclude" option takes precedence over the"Include"
option. However, whenever the "Include"option is used
all "Non-included" files are excluded anyway.
4. In the "Selection List Options" what is the difference between
the Include/Exclude files options and Include/Exclude
Path/Files on the "Selection List Options"?
The Include/Exclude Files options are used to restore
files that reside anywhere in the directory structure.
When used in conjunction with the Include/Exclude
Subdirectories options specific file paths can be restored
(see #2 above -- Restoring specific files).
The Include/Exclude Path/Files options are used to restore
files to the specific location in the directory structure
from which they were backed up. Regardless of the paths
specified the entire directory structure will be scanned.
Any subdirectories that were on the backup tape and not on
the server being restored will be created.
*****************************************************************
DISCLAIMER
Novell, Inc. makes no representations or warranties with respect to
any NetWare software, and specifically disclaims any express or
implied warranties of merchant ability, title, or fitness for a
particular purpose.
Distribution of any NetWare software is forbidden without the
express written consent of Novell, Inc. Further, Novell reserves
the right to discontinue distribution of any NetWare software.
Novell is not responsible for lost profits or revenue, loss of use
of the software, loss of data, costs of re-creating lost data, the
cost of any substitute equipment or program, or claims by any party
other than you. Novell strongly recommends a backup be made before
any software is installed. Technical support for this software
may be provided at the discretion of Novell.
*****************************************************************